Guides Sep 3, 2026 5 min read
How to answer a one-star review
Of the 31,000 low-rating replies sent through Ascent last year, 18% led the reviewer to raise the rating. What those replies had in common, starting with the clock.
Skyler Hayes Support
Last year developers used Ascent to answer 212,904 App Store reviews. About 31,000 of those were replies to one- and two-star reviews, and for those we can see something useful: whether the reviewer came back and changed the rating.
They do more often than you might expect. Across every low-rating reply sent through Ascent, 18% of reviewers later raised their rating, by an average of 2.6 stars. The replies that work have a few things in common, and so do the ones that do not.
Answer within a day
Speed matters more than wording. When the reply went out within 24 hours, 27% of reviewers updated their rating. After a week it was 8%. By then they have deleted the app, and the notification that you replied arrives for something they no longer have.
This is the reason low-rating alerts in Ascent are a push notification and not a line in tomorrow’s email. It is also the reason the reply box is in the notification.
Say what happened, then what to do
The reviewer wants to know two things: did you understand the problem, and is it fixed. A reply that answers both in two sentences beats one that apologizes for four.
Thanks for flagging this. 2.4.2 fixes the widget refresh and is live now, so one update should do it.
That reply, to a two-star review of Tidepool, is 20 words long. It names the bug, names the version that fixes it, and tells the reader what to do. The reviewer changed the rating to five stars the next morning.
If there is no fix yet, say so and say when you will know more. “We can reproduce it on iPad and are working on it this week” is a perfectly good reply. “We are sorry for any inconvenience” is not, because it could be pasted under any review of any app.
Never argue, even when you are right
Some one-star reviews are wrong. The feature exists; they did not find it. The charge was Apple’s, not yours. The temptation is to correct the record.
Remember who else reads the reply. It appears on your App Store page, under the review, for every prospective customer who scrolls that far. A reply that wins the argument still shows a developer arguing. Point to the feature, offer to help by email, and stop.
Keep a few replies ready
Most low ratings fall into five or six groups: a sync problem, a crash after an update, a subscription the reviewer did not expect, a missing feature, a refund request. Write a careful answer to each one once, when you are calm, and save it.
The rule we give for saved replies is to always change at least one line. Add the version number, the device they mentioned, the thing they were trying to do. Reviewers can tell when they have been sent a form letter, and so can the people reading over their shoulder.
Refunds are not yours to give
You cannot refund an App Store purchase yourself, and a surprising number of angry reviews come from people who think you refused to. Say plainly that Apple handles refunds, point them to Apple’s Report a Problem page, and tell them you hope they get it. It costs you nothing and it is, fairly often, the reply that turns one star into four.
The short version
- Reply inside 24 hours.
- Two sentences: what happened, what to do now.
- Name the version that fixes it.
- Do not argue in public.
- Edit one line of every saved reply.
